Forward error correction adjustments for c-v2x communications

ABSTRACT

A user equipment (e.g., C-V2X user equipment) can receive a transmission from a network device of a mobile network and decode the transmission using a first forward error correction code. The user equipment can determine an attribute of the transmission to determine a condition of the communication channel. Based on the condition of the communication channel, the user equipment can facilitate transmitting feedback to the network device, wherein the feedback is forwarded through the mobile network to an application server device that selects a second forward error correction code based on the feedback. The second forward error correction code can be transmitted to, and received by, the user equipment. The user equipment can use the second forward error correction code to decode subsequent transmissions.

RELATED APPLICATIONS

The subject patent application is a continuation of, and claims priorityto each of, U.S. patent application Ser. No. 16/869,034, filed May 7,2020, and entitled “FORWARD ERROR CORRECTION ADJUSTMENTS FOR C-V2XCOMMUNICATIONS,” which is a continuation of U.S. patent application Ser.No. 16/285,674 (now U.S. Pat. No. 10,686,558), filed Feb. 26, 2019, andentitled “FORWARD ERROR CORRECTION ADJUSTMENTS FOR C-V2XCOMMUNICATIONS,” the entireties of which applications are herebyincorporated by reference herein.

TECHNICAL FIELD

The present application relates generally to the field of wirelesscommunication and, more specifically, to the selection of a forwarderror correction code in cellular vehicle-to-everything (C-V2X)communications.

BACKGROUND

Cellular communications technology, including radio access technology,has grown rapidly and evolved since the launch of analog cellularsystems in the 1980s, starting from the First Generation (1G) in 1980s,Second Generation (2G) in 1990s, Third Generation (3G) in 2000s, andFourth Generation (4G) in 2010s (including Long Term Evolution (LTE) andvariants of LTE). Additionally, fifth generation (5G) access networks,which can also be referred to as New Radio (NR) access networks, arecurrently being developed and expected to fulfill the demand forexponentially increasing data traffic, and to handle a very wide rangeof use cases and requirements, including among others, mobile broadband(MBB) services, enhanced mobile broadband (eMBB) services, and machinetype communications (e.g., involving Internet of Things (IOT) devices).

As part of the expansion of the cellular platform for new services, andto keep track with the increasing needs of the automotive industry,functionality of the cellular infrastructure is being developed toprovide enhancements specifically for “vehicle-to-everything” (V2X)communications, which can comprise, for example, vehicle-to-vehicle(V2V), vehicle-to-infrastructure (V2I), vehicle-to-network, (V2N) andvehicle-to-pedestrian (V2P) communications. This development of thecellular infrastructure, functionality, and protocols (e.g., standards)for V2X communications is often referred to as cellular V2X (or C-V2X)communications. Vehicle-to-everything (V2X) communication leveragingcellular network infrastructure can provide reliable, actionableinformation flows with high definition quality services while paving theway for connected and autonomous driving into the near future. Thecollaboration between automotive and wireless telecommunicationstechnologies is driving the next generation of autonomous vehiculardesigns. With the initial C-V2X standards developed in 2017, the LTEplatform provides a means to offer new services to the automotiveindustry. LTE and 5G evolution will continue to further drive the C-V2Xstandardization efforts to meet the increasing needs of the automotivesector with new use cases that can significantly enhance the monitoringand tracking of driver behaviors, and enhance the efficiency as well assafety of intelligent transportation systems. The development andcommercialization of C-V2X technology involves multiple stake holders,including carriers, technology providers, automobile original equipmentmanufacturers (OEMs), and infrastructure vendors, to name somestakeholders, all working together to implement and showcase thebenefits and efficiency in the use of this technology for advancedvehicular connectivity and intelligent communications.

Due to its legacy capabilities and a clear roadmap with technologyevolution, the 5G automotive association has advocated the use ofcellular technologies to redefine and enhance the transportationservices connectivity model globally. The first associated standards ofC-V2X were introduced in the 3rd Generation Partnership Project (3GPP)standards Release 14. C-V2X technology is expected to drive theevolution of mobility networks and communications that can enableadvanced use cases such as autonomous driving, traffic flowoptimization, improved safety etc., thus playing a transformative rolein connected transportation communications services. LTE-based cellulartechnologies have enormous potential to drive innovative connectivityservices in automotive sector. LTE broadcast enhancements can facilitatevehicle-to-infrastructure (V2I), vehicle-to-vehicle (V2V) andvehicle-to-network (V2N) communications, leveraging traditional cellularnetworks. While standards-based C-V2X supports a variety of operationalmodes such as vehicle-to-infrastructure (V2I), vehicle-to-vehicle (V2V)and vehicle-to-network (V2N) communications, such systems and resultingIP multicast/broadcast/unicast services need to be carefully architectedto be able to utilize the mobility network infrastructure resourcescost-effectively while driving maximum return on investment foroperators. These services need to work concurrently with the legacymobility services to meet the high-performance demands associated withthe automotive use cases, as well as have the capability to meet thescale and needs of future use cases leveraging technologicaladvancements. V2I and V2N communications can greatly facilitate smartcities connectivity and control initiatives (ex: traffic, parking,metering updates, cancellations).

The above-described background relating to wireless networks is merelyintended to provide a contextual overview of some current issues and isnot intended to be exhaustive. Other contextual information may becomefurther apparent upon review of the following detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments of the subject disclosureare described with reference to the following figures, wherein likereference numerals refer to like parts throughout the various viewsunless otherwise specified.

FIG. 1 illustrates an example wireless communication system having anetwork node device (also referred to herein as a network node) and userequipment (UE), in accordance with various aspects and exampleembodiments of the subject application.

FIG. 2 illustrates an example centralized core network (CN) incomparison with a distributed CN implementing control plane and userplane separation, in accordance with various aspects and exampleembodiments of the subject application.

FIG. 3 illustrates the bandwidth and latency requirements for differentcommunication services, in accordance with various aspects and exampleembodiments of the subject application.

FIG. 4 illustrates an example of network slices, each havingcombinations of network functions, in accordance with various aspectsand example embodiments of the subject application.

FIG. 5 illustrates example components for C-V2X communications, inaccordance with various aspects and example embodiments of the subjectdisclosure.

FIG. 6 illustrates example components for C-V2X unicast and multicastcommunications, in accordance with various aspects and exampleembodiments of the subject application.

FIG. 7 illustrates example components for C-V2X communications whereinthe user plane and control plane are separated for a multimediabroadcast multicast services gateway (MBMS-GW) component and for abroadcast multicast service center (BMSC) component, in accordance withvarious aspects and example embodiments of the subject application.

FIG. 8 illustrates example components for C-V2X communications whereinthe user plane and control plane are separated for a MBMS-GW component,a BMSC component, a serving gateway (SGW) component, and a packet datanetwork gateway (PGW) in accordance with various aspects and exampleembodiments of the subject application.

FIG. 9 illustrates an example of the different network layers and theuse of different FEC codes across difference service areas, inaccordance with various aspects and example embodiments of the subjectapplication.

FIG. 10 illustrates an example of the different layers and the data pathfor evolved MBMS (eMBMS), in accordance with various aspects and exampleembodiments of the subject application.

FIG. 11 illustrates an example of flow monitoring and FEC adaptation inthe eMBMS, in accordance with various aspects and example embodiments ofthe subject application.

FIG. 12 illustrates an example of device cross-layer interactions, inaccordance with various aspects and example embodiments of the subjectapplication.

FIG. 13 illustrates an example of operations that can be performed by aC-V2X UE, in accordance with various aspects and example embodiments ofthe subject application.

FIG. 14 illustrates another example of operations that can be performedby a C-V2X UE, in accordance with various aspects and exampleembodiments of the subject application.

FIG. 15 illustrates another example of operations that can be performedby a C-V2X UE, in accordance with various aspects and exampleembodiments of the subject application.

FIG. 16 illustrates another example of operations that can be performedby a C-V2X UE, in accordance with various aspects and exampleembodiments of the subject application.

FIG. 17 illustrates an example block diagram of a mobile device that canexecute processes and methods, in accordance with various aspects andembodiments of the subject application.

FIG. 18 illustrates an example block diagram of a computer that canexecute processes and methods, in accordance with various aspects andembodiments of the subject application.

DETAILED DESCRIPTION

The subject application is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. The following description and the annexed drawings set forthin detail certain illustrative aspects of the subject matter. However,these aspects are indicative of but a few of the various ways in whichthe principles of the subject matter can be employed. Other aspects,advantages, and novel features of the disclosed subject matter willbecome apparent from the following detailed description when consideredin conjunction with the provided drawings. In the following description,for purposes of explanation, numerous specific details are set forth inorder to provide a more thorough understanding of the subjectapplication. It may be evident, however, that the subject applicationcan be practiced without these specific details. In other instances,structures and devices are shown in block diagram form to facilitatedescribing example embodiments.

The methods and operations (e.g., processes and logic flows) describedin this specification can be performed by devices (e.g., networkmanagement device, gateway device, etc.) comprising programmableprocessors that execute machine executable instructions (e.g., computerprogram product, computer-readable instructions, software, softwareprograms, software applications, software modules, etc.) to facilitateperformance of the operations described herein. Examples of such devicescan be devices comprising circuitry and components as described in FIG.10.

The cellular industry is striving to develop cellular V2X (C-V2X)technology and is seeking to evolve the cellular carrier's mobilitynetwork infrastructure to support advanced software features related toevolved multimedia broadcast multicast services (eMBMS) and nextgeneration new radio technologies to transport efficient unicast as wellas multicast user data in switched modes.

The present application relates to the improvement of vehicularconnectivity and integrated communications delivery model with a varietyof mobile device platforms that can be embedded in the next-generationautomotive vehicles.

While standards-based C-V2X supports a variety of operational modes suchas vehicle-to-infrastructure (V2I), vehicle-to-vehicle (V2V) andvehicle-to-network (V2N) communications, such systems and resulting IPmulticast/broadcast/unicast services need to be carefully architected tobe able to utilize the mobility network infrastructure resourcescost-effectively while driving maximum return on investment foroperators. These services need to work concurrently with the legacymobility services to meet the high-performance demands associated withthe automotive use cases as well as have the capability to meet thescale and needs of future use cases leveraging technologicaladvancements.

The increasing demand of connected cars with embedded multi-mode mobiledevice platforms to obtain rich communications and navigationcapabilities via advanced cellular technologies such as LTE and 5G leadsto significant challenges. Connected cars and autonomous driving usecases in smart cities might require high definition graphics intensivemap images in real time broadcasted to them with minimal latency andhigh quality to be able to maneuver accurately enhancing the roadsafety. In addition, high valued services such as live-streaming, smartparking and important map updates via file downloads should be deliveredwith high customer satisfaction.

In a traditional broadcast service delivery, devices tuned to receivingbroadcasts in a given Multicast Broadcast Single Frequency Network(MBSFN) serving area are often limited in terms of their service qualityduring mobility based on the dynamics of the correction patternsemployed by the LTE modems at the various signal processing layers.While messages can be broadcasted from a plurality of V2X applicationservers to several automotive vehicles simultaneously in the downstream,the unicast uplink transfers from such vehicles are not impacted. Due tothe complex dynamics of the radio conditions, multicasting in apoint-to-multipoint environment with bandwidth-limited networks becomesextremely challenging. Specifically, due to the mobility patternsassociated with these automotive device platforms when receivingmulticast user data across the eMBMS broadcast serving areas, and theircorresponding radio environments by virtue of their spectrumallocations, static methods for forward error correction (FEC) in agiven broadcast serving area will not suffice in the mobile datatransport delivery.

In a typical FEC scheme, redundant packets are generated by an FECencoder and transmitted along with source packets. As an example, on thetransmitter side, a bit string 01 can be encoded into a longer bitstring, say 00111. Once the receiver receives the encoded bit string, ituses a decoder to decode the string (00111) into the original source bitstring 01. If one of the bits was transmitted in error (e.g., 00111 wastransmitted, but resulted in a reception of 00011), the receiver sidecan still deduce that the source bit string is 01, because the corruptedstring 00011 is still more similar to the encoded codeword for 01, whichis 00111, than it is to other codewords, such as 00000 or 11110. An evenlonger codeword, say with eight characters instead of five (e.g.,01100110), while resulting in more bits being transmitted, provides formore bits to enable a detection of an error. Compared with the automaticrepeat request (ARQ), which retransmits lost data using anacknowledgement process, FEC is usually preferred for real-time videoapplications due to lower end-to-end delay.

However, FEC methods at the physical layer and/or application layersthat have been applied for point-to-point links will not work uniformlyfor live streaming and file downloads in a multicast transport scenario.With the static FEC methods, wherein the FEC rate in a given region hasbeen pre-determined at the head-end based on certain network designassumptions, the end user broadcast data services quality could beimpacted with mobility between serving areas. In a traffic congestedcell, the situation becomes worse with mobility when there is no meansto adapt the network functions via suitable interactions between radioaccess and core network nodes. These static FEC methods do not provide ameans for operators to achieve the best return on investment for theirscarce spectrum and overall network resources investments.

To alleviate such limitations associated with static mapping of FEC in ageo-fenced serving area pre-provisioned at the broadcast core networkhead-end, and to provide enhanced end user C-V2X service levelexperience in connected smart-cars and drive widespread adoption ofC-V2X with the next generation mobility technologies, the presentapplication relates to a software application intelligence layer (e.g.,an intelligent software agent based cross-layer monitoring mechanism) inplace within the embedded device platforms (e.g., middleware) in theautomotive vehicles (connected cars). This approach can be seen assimple, flexible and adaptable in real-time based on the mobilitynetwork dynamics, closed-loop radio network monitoring, and tightcontrol, as well as take into account geo-targeted broadcast/unicastapplication/services requirements.

In example embodiments, a network device executing the intelligentsoftware agent can closely monitor the northbound and southboundmessaging interactions that take place between the applications andunderlying signal processing layers associated with the mobilitytechnology, as well as the resources allocated in a targeted region.With integrated analytics capability, the network device can be operablefor monitoring, correlating cross-layer interactions, trending thedynamics of the radio channel conditions per spectral allocation for thetransported multicast user data. Such an agent can self-triggerautomated notification alerts to request enhancements from the mobilitycore network on-demand to aid in the adaptations of the FEC (e.g.,facilitate the selection of a more suitable codeword if conditions callfor it), based on the cell efficiency metrics as well as the eMBMSserving area dynamics surrounding the specific automotive vehicle'smobility path.

Further, the example integrated agent in the device middleware canperiodically track such performance at the individual unicast/broadcastservice flow level via correlated mapping with critical attributes(e.g., application layer—streams, duration, battery life, securitycontrols, signal processing layer-serving area geo-fencing, spectrumresources utilized for broadcast/unicast, RSSI, SNR, FEC rates in agiven serving area) and maintain a transient inventory of the mobilitypath for a device. By providing on-demand threshold-based triggers viamobile originated unicast data connections, the connected-car deviceplatform can be in a position to securely relay its behavioral-servicedelivery and quality patterns and tightly interwork with the networkfunctions to adapt its usability conditions to derive more optimaldownstream broadcast service quality.

FIG. 1 illustrates some example components of a typical wirelesscommunication system 100 (also referred to as wireless system 100,mobile system 100, mobile communications system 100). In exampleembodiments (also referred to as non-limiting embodiments), wirelesscommunications system 100 can comprise a mobile (also referred to ascellular) network 106, which can comprise one or more mobile networkstypically operated by communication service providers. The wirelesscommunication system 100 can also comprise one or more user equipment(UE) 102 _(1-N) (also referred to as UE 102). UE 102 _(1-N) cancommunicate with one another via one or more network node devices (alsoreferred to as network nodes) 104 _(1-N) (referred to as network node104 in the singular) of the mobile network 106. The dashed arrow linesfrom the network nodes 104 _(1-N) to the UE 102 _(1-N) representdownlink (DL) communications and the solid arrow lines from the UE 102_(1-N) to the network nodes 104 _(1-N) represent uplink (UL)communications.

UE 102 can comprise, for example, any type of device that cancommunicate with mobile network 106, as well as other networks (seebelow). The UE 102 can have one or more antenna panels having verticaland horizontal elements. Examples of a UE 102 comprise a target device,device to device (D2D) UE, machine type UE, or UE capable of machine tomachine (M2M) communications, personal digital assistant (PDA), tablet,mobile terminal, smart phone, laptop mounted equipment (LME), universalserial bus (USB) dongles enabled for mobile communications, a computerhaving mobile capabilities, a mobile device such as cellular phone, adual mode mobile handset, a laptop having laptop embedded equipment(LEE, such as a mobile broadband adapter), a tablet computer having amobile broadband adapter, a wearable device, a virtual reality (VR)device, a heads-up display (HUD) device, a machine-type communication(MTC) device, and the like. UE 102 can also comprise IOT devices thatcommunicate wirelessly. In example embodiments of the presentapplication, the UE 102 can be a C-V2X wireless device within a vehicle(e.g., C-V2X UE enabling C-V2X communications). Or, the vehicle itselfcan be said to be a C-V2X UE. In example embodiments of the presentapplication, as will be described below, a C-V2X UE can comprise asoftware application intelligence layer (e.g., an intelligent softwareagent based cross-layer monitoring mechanism) in place within theembedded device platforms (e.g., middleware) of the C-V2X UE.

Mobile network 106 can include various types of disparate networksimplementing various transmission protocols, including but not limitedto cellular networks, femto networks, picocell networks, microcellnetworks, internet protocol (IP) networks, Wi-Fi networks associatedwith the mobile network (e.g., a Wi-Fi “hotspot” implemented by a mobilehandset), and the like. For example, in at least one implementation,wireless communications system 100 can be or can include a large scalewireless communication network that spans various geographic areas, andcomprise various additional devices and components (e.g., additionalnetwork devices, additional UEs, network server devices, etc.).

Still referring to FIG. 1, mobile network 106 can employ variouscellular systems, technologies, and modulation schemes to facilitatewireless radio communications between devices (e.g., the UE 102 and thenetwork node 104). While example embodiments might be described for 5GNew Radio (NR) systems, the embodiments can be applicable to any radioaccess technology (RAT) or multi-RAT system where the UE operates usingmultiple carriers. For example, wireless communications system 100 canbe of any variety, and operate in accordance with standards, protocols(also referred to as schemes), and network architectures, including butnot limited to: global system for mobile communications (GSM), 3GSM, GSMEnhanced Data Rates for Global Evolution (GSM EDGE) radio access network(GERAN), Universal Mobile Telecommunications Service (UMTS), GeneralPacket Radio Service (GPRS), Evolution-Data Optimized (EV-DO), DigitalEnhanced Cordless Telecommunications (DECT), Digital AMPS (IS-136/TDMA),Integrated Digital Enhanced Network (iDEN), Long Term Evolution (LTE),LTE Frequency Division Duplexing (LTE FDD), LTE time division duplexing(LTE TDD), Time Division LTE (TD-LTE), LTE Advanced (LTE-A), TimeDivision LTE Advanced (TD-LTE-A), Advanced eXtended Global Platform(AXGP), High Speed Packet Access (HSPA), Code Division Multiple Access(CDMA), Wideband CDMA (WCMDA), CDMA2000, Time Division Multiple Access(TDMA), Frequency Division Multiple Access (FDMA), Multi-carrier CodeDivision Multiple Access (MC-CDMA), Single-carrier Code DivisionMultiple Access (SC-CDMA), Single-carrier FDMA (SC-FDMA), OrthogonalFrequency Division Multiplexing (OFDM), Discrete Fourier TransformSpread OFDM (DFT-spread OFDM), Single Carrier FDMA (SC-FDMA), FilterBank Based Multi-carrier (FBMC), zero tail DFT-spread-OFDM (ZTDFT-s-OFDM), Unique Word OFDM (UW-OFDM), Unique Word DFT-spread OFDM (UWDFT-Spread-OFDM), Cyclic Prefix OFDM (CP-OFDM), resource-block-filteredOFDM, Generalized Frequency Division Multiplexing (GFDM), Fixed-mobileConvergence (FMC), Universal Fixed-mobile Convergence (UFMC), MultiRadio Bearers (RAB), Wi-Fi, Worldwide Interoperability for MicrowaveAccess (WiMax), and the like.

Still referring to FIG. 1, in example embodiments, UE 102 can becommunicatively coupled (or in other words, connected) to a network node104 of the mobile network 106. Network node 104 can have a cabinet andother protected enclosures, an antenna mast, and multiple antennas forperforming various transmission operations (e.g., MIMO operations). Eachnetwork node 104 can serve several cells, also called sectors, dependingon the configuration and type of antenna. Network node 104 can compriseNodeB devices, base station (BS) devices, mobile stations, access point(AP) devices, and radio access network (RAN) devices. Network node 104can also include multi-standard radio (MSR) radio node devices,including but not limited to: an MSR BS, an eNode B device (e.g.,evolved NodeB), a network controller, a radio network controller (RNC),a base station controller (BSC), a relay device, a base transceiverstation (BTS), an access point, a transmission point (TP), atransmission/receive point (TRP), a transmission node, a remote radiounit (RRU), a remote radio head (RRH), nodes in distributed antennasystem (DAS), and the like. In 5G terminology, the network node isreferred to by some as a gNodeB (gNB) device, which provides NR userplane and control plane protocol terminations towards the UE, andconnects to the 5G core.

Referring now to FIG. 2, example embodiments of a mobile network of thepresent application can employ an architecture in which a user plane andcontrol plane are separate, wherein complex control plane functions areabstracted from forwarding elements, simplifying user plane operationsby relocating control logic to physical or virtual servers. Each planecarries a different type of traffic and can be implemented as overlaynetworks that runs independently on top of one another, althoughsupported by its infrastructure. The user plane (sometimes known as thedata plane, forwarding plane, carrier plane, or bearer plane) carriesthe network user traffic, and the control plane carries signalingtraffic. Typical control-plane functionality includes capabilities suchas the maintenance of location information, policy negotiation andsession authentication. In example embodiments, the planes can beimplemented in the firmware of routers and switches. As shown in FIG. 2,a mobile network (e.g., mobile network 106) with a centralized corenetwork (CN) can be decentralized, resulting in a distributed CN, whichacts as a controller in a mobile communication network, and performsunderlying tasks required for providing mobile communication services(e.g., user authentication, data transmission, etc.). To abstract thenetwork resources from the underlying physical hardware, the controlplane and user plane are separated, abstracting the network resourcesfrom the underlying physical hardware. This separation allows user-planefunctionality to move to the network edge, and management functionalityto remain at the core.

For example, as shown in FIG. 2, a gateway (GW) 205 in a centralized CNcan, in a distributed CN, be separated into a GW-CP 210 for the controlplane and GW-UP 215 for the user plane, wherein the user planefunctionality is closer to the network edge. In this distributed CN, thephysical core can be virtually separated and relocated in the networkinto multiple virtual core networks using virtualization technology.This software-defined networking (SDN) approach, can be complimentary toa network functions virtualization (NFV) approach, in which a virtualnetwork function (VNF) is responsible for handling specific networkfunctions (NFs) that run on one or more virtual machines (VMs) on top ofthe hardware networking infrastructure (e.g., routers, switches, etc.).Individual VNFs can be connected or combined to offer a particularnetwork communication service. Both SDN and VNF can facilitate theimplementation of network slicing (described further below). FIG. 7 andFIG. 8 below describe some more components that can be separated intocontrol and user planes.

Network services can be handled by decentralized virtual networkfunctions, called network slices, which are instantiated either for aspecific, dedicated service, or group of services, utilized bysubscribers or large enterprises. These slices are made to performspecific tasks depending on the location, quality of service (QoS) andcapacity of a given service. Thus, instead of having one network thatserves all devices on the network and performs all services, a singlephysical network can be sliced into multiple virtual networks that candraw from both CN and radio access network (RAN) resources to provide aspecific service. In this manner, network slices can be specificallyconfigured to support a multitude of use cases and new services. Eachuse case involves performance requirements that vary enormously. Asshown in FIG. 3, the bandwidth and latency related to each service canvary. IOT sensors and meters 305 might require service that is lowbandwidth and medium latency. Smartphones 310 might require highbandwidth and medium latency. Autonomous vehicles 315 relying on V2Xmight require low latency but not necessarily a high bandwidth for everycommunication application. Virtual reality video streaming 320 thatsupports video games and live sporting events might require a very highbandwidth, but low latency. As such, different use cases place differentrequirements on the network in terms of functionality. Each specificservice requires different resources, receiving a specific set ofoptimized resources and network topology that covers certain servicelevel agreement specified factors for delivering the service, includingsuch factors as such as connectivity, speed, latency and capacity. Forexample, for autonomous vehicle services 320, Ford, Lyft, or Chevy mighteach have a different service level agreement with a network provider tosupport their autonomous vehicle communication services.

Referring now to FIG. 4, a service orchestration manager 405 caninstantiate network slices 410 _(1-N) of the network comprisingcombinations of vNFs (virtual network functions (NFs)) on defaulthardware (HW) in order to reduce the network complexity, and providecapital savings on proprietary HW and software. Each network slice canbe instantiated, depending on, for example, the location (such asdedicated slice close to a large customer enterprise) or quality ofservice (e.g., high QoS slice for a premium service). These slices arepart of cloud network running on a default hardware with givenlimitations such as number of dedicated processors and memory, etc. Asshown in FIG. 4, with network slicing, each of these services can bedelivered over the same common physical network on multiple virtualnetwork slices to optimize use of the physical network. A slice#1 410 ₁can be instantiated to support IOT meters and sensors 305. A slice#2 410₂ can serve smartphones. A slice#3 410 ₃ can serve autonomous vehicles315. A slice#4 410 ₄ can support virtual reality video streaming 320. Nnumber of slices in the network (e.g., slice#N 410 _(N)) can beinstantiated to support other services. Each network slice can comprisean independent set of logical, network functions NFs 415 _(1-N) (alsoreferred to herein as tasks) that support the requirements of particularservices (e.g., the term “logical” can refer to software), with some NFsthat can be shared across multiple slices (e.g., NF1 415 ₁ is commonacross the slices), while other NFs are tailored to a particular networkslice. An NF can comprise network nodes functionality (e.g. sessionmanagement, mobility management, switching, routing functions) which hasdefined functional behavior and interfaces. Thus, NFs can be implementedas a network node (e.g., network node 104) on a dedicated hardware or asvirtualized software functions. The service orchestration manager device405 can perform selection functions that pair the resources and networktopology (e.g., RAN and fixed access, terminal, transport, and CNresources) needed for the specific service and traffic that uses theslice. In this way, functions such as speed, capacity, connectivity andcoverage can be allocated to meet the specific demands of each use case.Not only can a network slice be specifically instantiated for certainservices, it can be reused.

In a typical C-V2X delivery network, as shown in FIG. 5, a C-V2Xreference architecture can use eMBMS broadcast core network functionsin, for example, an LTE mobility network, to deliver file downloads anddeliver live streaming from the content source (C-V2X application server505) to a large number of C-V2X UEs targeted in specific regions (e.g.,UEs 102 _(1-N), wherein a UE 102 can be enabled to communicate accordingto C-V2X standards, shown in the singular in FIG. 5 as C-V2X UE 505)C-V2X UE 505 can be a device in, or embedded in, for example a vehicle.A vehicle enabled with C-V2X communications can also be considered as aC-V2X UE. A variety of C-V2X UE device platforms could be used thatsupport the appropriate eMBMS chipset/modem and application clientcapabilities. These could be embedded in the automotive vehicle withintheir traffic control unit. While simple clients with standard modem andapplication functions can deliver the eMBMS user services, they areoften faced with challenges due to the dynamics of the radio conditions.

In this typical architecture as shown in FIG. 5 (e.g., a mobile network106 implementing, for example, an LTE network), the C-V2X applicationserver 510 triggers the broadcast (e.g., files, video streaming packets)to the head-end broadcast multicast service center (BMSC 515). Locatedat the core of the network, the BMSC manages the interface with contentproviders, including managing billing and the content to be transmittedover the mobile network. The BMSC initiates LTE broadcast sessionestablishment with the multimedia broadcast multicast service gateway(MBMS-GW 520), which in turn interacts with a management mobility entity(MME) and eNodeB 530 to complete the process. As mentioned above, anetwork node 104 in LTE terminology can be referred to as an eNodeB 530.Control plane eMBMS signaling can be initially established in themobility core network via multiple signaling interfaces between thevarious network functions: C-V2X Application Server-BMSC via theMB2-C/xMB-C interface, BMSC-MBMS GW via the SGmb interface, MBMS GW-MMEvia the Sm interface, MME-eNB via M3 interface and eNB-UE via the Uuinterface. The radio access network (RAN) eNodeB 530 joins the MBMS GWupon session completion to start receiving the user data from the MBMSGW via the M1 interface. User data from C-V2X-Application Server istransferred to BMSC via MB2-U/xMB-U interface, and from the BMSC to MBMSGW via the SGi-mb interface. With multiple interfaces involved in thecontrol plane setup, the session establishment times could be longerdepending on the geographical location of the various core networkfunctions.

Additionally, the RAN can be provisioned with the band specificinformation for associated LTE-B data transfers—statically ordynamically based on external triggers from spectrum management systems,based on their availability and utilization in a given geographic area.UE devices (C-V2X UE 505) can tune into the broadcast as long as theysupport the client and are in the multi-frequency single-frequencynetwork (MBSFN) spectral radio coverage area.

Moving on to FIG. 6, the network functions and components supportingboth unicast and broadcast services are shown. Unicast data connectionestablishments follow the standard packet data network (PDN) connectionsetup process with bearer establishments. Contrary to unicastconnections that require a specific access point name (APN), broadcastservices do not require any APN subscription within the home subscriberserver (HSS) systems. The broadcast services are triggered by the C-V2Xapplication server (e.g., C-V2X application server 510) within thecontent delivery network at operator defined intervals and for a givenduration in a given location.

Still referring to FIG. 6, core network functions such asBMSC/MBMS-GW/MME/SGW/PGW and AS can be virtualized and can be hosted ina cloud data center. In FIG. 6, the path of unicast data moves through apacket data network gateway (PGW) and a serving gateway (SGW). These twocomponents performing the PGW and SGW functions are shown as PGW 605 andSGW 610 in FIG. 6. These functions can be centralized or distributedbased on operator's deployment model for mobility services delivery. Asubset of these functions can be co-located closer to the RAN clusterswhere appropriate to reduce the latency aspects of targeted multicastuser plane data transfers in a given broadcast serving area. RAN nodescan be LTE-broadcast capable in concentrated areas serving both unicastand multicast data transfers (e.g., dashed lines in FIG. 6) acrossmultiple spectrum allocations and availability in a given geographicarea. Spectrum analysis and monitoring can ensure proper utilization ofbroadcast and unicast resources in real time to provide maximum returnon investment (ROI) to operators.

While the broadcast core network components can be hosted along with theunicast core network functions, such deployments may not necessarily beoptimal for flexible service offerings. All core functions could bephysical or virtualized in data centers and could be deployed in acentralized or distributed configurations to meet specific operatorneeds. A subset of the core network functions, such as broadcast nodes,could be localized to meet the stringent service quality needs.

Due to the heavy control plane and user data forwarding interactionsrequired to support a mix of unicast and broadcast services, the corenetwork components with their traditional integrated control and userplane functions may be limited with respect to their capacity andscalability while supporting geo-redundancy. To address the scale,multiple functions need to be replicated in several data centerlocations which could become very expensive. Even with NFV/SDNtransformation, such virtual functions may need to be instantiated atseveral data centers and may still be limited by the underlying networkinfrastructure reliability when supporting a mix of complex protocolsand their associated packet handling functions at the transport layer.Additionally, disjoint unicast and broadcast configurations operating ina standalone manner is not optimal and could result in a networkutilization imbalance as well as being prohibitively expensive due tospectrum allocations in certain deployment situations.

The present application facilitates the mitigation of the abovesituation by separating control and user plane functions for broadcastcore network functions as shown in FIG. 7. While 3GPP Rel. 14 standardshave recently completed the control and user plane separation (CUPS)feature in the EPC core network for unicast data services, no such modeland/or feature capability exists for broadcast (e.g., multicast) corenetwork functions. Referring to FIG. 7, in example embodiments inaccordance with the present application, there two signaling interfacesSxe and Sxd, between the MBMS GW Control and User Plane functions aswell as between the BMSC Control and User plane functions areestablished. As shown in FIG. 7, the MBMS-GW 520 and the BMSC 515 can beseparated based on control plane and user plane functionality. Thus, theBMSC 515 can be separated into a BMSC-Control Plane (e.g., BMSC-CP 705)and BMSC-User Plane (e.g., BMSC-UP 710), and the MBMS-GW 520 can beseparated into a MBMS-GW-Control Plane (MBMS-GW-CP 715) and MBMS-GW-UserPlane (MBMS-GW-UP 720). The separation also results in an interfacebetween the BMSC-CP and BMSC-UP (Sxe 725), and an interface between theMBMS-GW-CP and MBMS-GW-UP (Sxd 730). Such separation offers flexibilityfor operators to deploy broadcast control and user plane functions in acentralized and/or distributed configuration and scale independentlybased on as needed basis in targeted locations. Localizing user planebroadcast functions closer to the RAN can significantly benefitdeployments and can simplify the mobility network infrastructure costeconomics. Several advantages can result for mobile operators as well ascontent providers by being able to competitively position themselves fordisruptive localized and targeted broadcast services. Such networkconfigurations can drive reduced backhaul requirements, benefiting livestreaming service flows that are extremely sensitive to latency, delay,radio link errors and channel switching times. By monitoring the controland user plane functions in conjunction with the intelligence receptionreports received from the end points, viewing experiences could befurther enhanced locally that could in turn drive services adoption.

FIG. 8 shows example embodiments in accordance with the presentapplication of an integrated evolved control and user plane separation(eCUPS) for more efficient and dynamic unicast/multicast flow transfer,wherein, the PGW (e.g., PGW 605) and SGW (e.g., SGW 610) are alsoseparated into control plane and user plane. Thus, as shown in FIG. 8,the PGW can be separated into a PGW-User Plane (PGW-UP 805) and aPGW-Control Plane (e.g., PGW-CP 810), and the SGW can be separated intoan SGW-User Plane (e.g., SGW-UP 815) and SGW-Control Plane (e.g., SGW-CP820). With integrated control and user plane functions separationsupporting both unicast and broadcast services as shown in FIG. 8,operators have even better flexibility in terms of network deploymentand operations benefiting service dynamics in targeted locations. Suchan architecture also facilitates independent scaling between control anduser plane functions for simultaneous unicast and multicast/broadcastsession/connection establishments as well as associated user datatransfers while not impacting legacy functionality of the existing nodesundergoing the functional split.

As mentioned above with respect to FIG. 4, network slices can bespecifically configured to support a multitude of use cases and newservices. Mobile operators could leverage NFV/SDN principles to slicethe control/user plane network functions for unicast/broadcast andorchestrate such functions in the most desirable high-densityenvironments (concerts, trade shows, school/college game events etc.)where the impact is extremely high with respect to delivering superiorservice quality. In FIG. 9, where the users with specific device typesare distributed across multiple broadcast serving areas within a givenMBSFN region, localized core user plane deployments can yield muchbetter performance results during mobility. Based on a closed loopmonitoring within the devices (e.g., C-V2X UEs) in targeted broadcastareas and reports of service quality, user plane broadcast functions canbe scaled locally and independently of the control plane broadcastfunctions to enhance the end user experience. Based on the eMBMS servicequality reception reports received from connected cars and processed bythe C-V2X application server, it can immediately trigger enhancedapplication layer FEC (AL-FEC) rates to localized BMSC-CP, which in turncan send updates in targeted broadcast serving areas where the endpoints can selectively use that information based on dynamics of theirradio conditions.

As an example, as shown in FIG. 9, eMBMS communications can involveseveral layers, for example, the application/service layer 905, themobility core network layer 910, the mobility transport network layer915, and the radio access network layer 920 (which the network nodes 104are part of). At the application/service layer 905, a C-V2X applicationserver can transmit, for example, video data, destined for C-V2X UEs indifferent service areas. Connected cars during mobility can crossbroadcast serving areas (service area 1 925, service area 2 930, servicearea 3 935, service area N 940) as shown in FIG. 9, and may operate inmulti-mode based on their embedded device platform capabilities. Theymay be able to switch from one device category to another (ex: CAT 4 toCAT 6 or CAT 19 or CAT 1) based on the intelligence synthesized by themiddleware that works across the modem-application layers at the serviceflow level, as shown in FIG. 10 and FIG. 11. In each serving area, dueto transmission conditions, one FEC code might be more suitable thananother FEC code. Example embodiments of the present application allowfor the selection of different FEC codes for different service areas,based on feedback provided, triggered by an analysis of the transmissionconditions experienced by the C-V2X UE.

As shown in FIG. 10, the application/service layer 905 (e.g., anapplication server device, such as C-V2X application server 510)triggers the broadcast content to be delivered to the end user (e.g.,C-V2X UE 5051, C-V2X UE 505 ₂). The LTE-broadcast headend receives thedata feed to be broadcasted to device/s in a given geographic area(MBSFN). Core, Transport and Access network functions are invoked tosupport the LTE broadcast session establishment. The eNB can beLTE-broadcast capable and operate with multiple licensed-unlicensedfrequency bands/carriers. All supported bands might not be used forbroadcast data transfer based on provisioning and service requirements.The eNB has the intelligence to schedule downlink (DL) user datatransfers in a given band (By) upon joining the multicast group with theMBMS GW in the core network using the M1 interface. The C-V2X UE istuned to both bands Bx and By being transmitted by eNB. Bx can be usedfor DL/UL notifications/triggers from the eNB/UE for an impendingbroadcast data transfer/related communication. Actual user data transferis received in band By only to meet the service criteria.

Referring now to FIG. 11, example embodiments of a C-V2X UE (e.g., C-V2XUE 505) can provide feedback to the mobile core, leading to anadjustment to application layer forward error correction (AL-FEC), aswill be described further below. Given the various degrees of freedomavailable in the network with spectrum allocation, active carriers,resource utilizations, aggregate capacity, services priority, FEC rateallocation and adaptation per flow in use, radio channel conditions, andservice quality per active flow, the C-V2X UE 505 executing middlewarein the C-V2X UE 505 can trigger generation of reception reports ornotifications based on policy driven rules and/or threshold alerts(e.g., if a quality of service becomes low, or an SNR becomes high, orif a certain number of errors in a time period has been reached, etc.).The C-V2X UE can engage in cross-layer analysis (e.g., examine thephysical layer, service layer, etc.) so as to correlate differentattributes within the layers and make a determination as to whether theFEC code that is currently being used is optimal, or whether anadjustment needs to be made (e.g., use another FEC rate, or another FECcode, that would be more optimal). The reports and alerts (e.g.,feedback) can be transmitted via a unicast uplink (UL) channel to thelocalized broadcast core network head-end. Such feedback can beextremely conducive for the network to be intelligent, and drive controlof the application layer attributes, including application layer forwarderror correction (AL-FEC) in the devices in coordination with the modemlayer FEC on a per-flow basis within a given serving area. Additionally,a broadcast resource mapping function component 1105, can track all theresource utilizations across the layers, which gives the C-V2X UE (e.g.,the software agent within the device) a way to correlate all thedifferent cross-layer attributes, which can allow it to provide anadjustment to the output FEC.

In example embodiments in accordance with the present application, aC-V2X UE (e.g., C-V2X UE 505) comprising a processor and a memory thatstores executable instructions (e.g., middleware in example embodiments)that, when executed by the processor, enable the C-V2X UE 505 to monitorthe conditions of transmissions to the C-V2X UE, and based on ananalysis of parameters associated with the transmissions, providefeedback regarding which forward error correction code to use fordecoding received transmissions. The feedback can be sent through thenetwork core to an application layer server device (e.g., C-V2Xapplication server 510) that broadcasts content to C-V2X UEs. In exampleembodiments, the C-V2X UE can receive a transmission (e.g., livestreaming content) from a network device (e.g., network node) of amobile network via a communication channel. The C-V2X UE can decode thistransmission using a forward error correction code (e.g., first forwarderror correction code). The C-V2X UE can determine one or moreattributes of the transmission to determine a condition of thecommunications channel The attribute might relate to a physicalcondition of the channel. For example, the C-V2X UE can determine asignal to noise ratio (SNR) relate to the transmissions. The attributemight relate to a quality of service (e.g., a measured bandwidth).Another attribute might be the number of times there were errors in thetransmissions (e.g., based a per flow basis, or based on a periodicbasis). Each time that the number of bits in a transmission do not matchup with the bits of a FEC code can be counted. If the SNR is too high,or the bandwidth is lower than an acceptable quality of service, or ifthere are too many errors, the condition of the communications channelcan be determined to be poor, or not optimal. The C-V2X UE executingthis middleware software can engage in cross-layer analysis andcorrelation, looking at all the attributes of these layers together todetermine whether an adjustment in the FEC rate (e.g., select adifferent FEC code, for example) can be made that results in moreoptimum transmissions (e.g., reduction in errors in transmissions).

As such, based on the condition of the communication channel, the userequipment can facilitate transmitting feedback to the network device(e.g., network node 104), wherein the feedback is forwarded by thenetwork device to an application server device that selects a secondforward error correction code based on the feedback. As an example, ifthe feedback indicates that the channel conditions are poor, theapplication server device can select a second forward error correctioncode (e.g., one in which each FEC code word is longer) to be used by theC-UE device to decode subsequent transmissions. The application servercan, in example embodiments, send the FEC code to be used by the C-V2XUE. In example embodiments, the C-V2X UE acknowledges the receipt of theFEC code by sending an acknowledgement to the application server. TheC-V2X application server can then begin sending transmissions encodedwith the newly selected FEC, and the C-V2X UE can decode thetransmissions with the newly selected FEC. The new FEC correction codecan not only be transmitted to the C-V2X UE, but can be broadcast toother C-V2X UE devices in the same service area, as those devices mightbe experiencing similar transmission conditions.

In other example embodiments, if the C-V2X UE already has stored in itsmemory the FEC codes, after evaluating the feedback and selecting a FECcode, the application server can send a message to the C-V2X UEindicating which FEC code the C-V2X UE should use for futuretransmissions (at least until monitored channel conditions warrantanother change in the FEC being used). The C-V2X UE acknowledges thereceipt of the indication message by sending an acknowledgement to theapplication server. The application server can then begin sendingtransmissions encoded with the newly selected FEC, and the C-V2X UE candecode the transmissions with the newly selected FEC.

In other example embodiments, it is the C-V2X UE that select the FEC tobe used, and either sends the selected FEC code to the applicationserver, or sends a message indicating to the application server whichFEC code the application server should use for encoding subsequenttransmissions from the application server to the C-V2X UE. Theapplication server can send an acknowledgement indicating that it hasreceived the message indicating which FEC code it should use. Once theacknowledgement has been sent, the application server can begin sendingtransmissions encoded with the FEC code selected by the C-V2X UE.

Now referring to FIG. 12, in example embodiments, the middlewarecorrelation engine embedded in the device platform facilitates the C-V2XUE 505′s monitoring capability on a per-flow level via cross-layerinteractions, and then, based on policy driven threshold alerts (e.g.,if an SNR reaches a threshold, or a bandwidth dips to a threshold,etc.), enables the C-V2X UE to provide of feedback to the network via adedicated PDN connection using a specific APN. The PGW then notifies thetargeted application server (C-V2X application server 510) destined toreceive such feedback (e.g., a report, dashboard).

Once the C-V2X application server receives the feedback (e.g., report,dashboard), it can take proactive action to broadcast the FEC rateadaptations across the serving areas via the localized broadcast corenetwork. By providing an on-demand threshold-based triggers per flow viamobile originated unicast data connections to the content deliverynetwork head-end, the connected-car device platform is able to securelyrelay its behavioral-service flow delivery and quality patterns andtightly interwork with the mobility network functions to adapt itsusability conditions to derive a more optimal downstream quality ofservice.

In example embodiments, a UE (C-2VX UE 505), comprising a processor anda memory that stores executable instructions that, when executed by theprocessor, facilitate performance of operations, including thoseoperations/methods as described above, and also below in FIGS. 13-16. Ineach of these operations, steps or aspects described in one operationcan be substituted or combined with steps and aspects with respect tothe other operations, as well as features described, unless contextwarrants that such combinations or substitutions are not possible.Further, if a feature, step, or aspect is not described with respect toexample operations, this does not mean that said feature, step, oraspect is incompatible or impossible with respect to those operations.As such, the example operations of the present application describedabove and below are not necessarily limited to the steps, features, oraspects that are described with respect to those example operations.

FIG. 13 illustrates a flow diagram of example operations 1300 that canbe performed, for example, by a user equipment (e.g., C-V2X UE 505)comprising a processor and a memory (e.g., a machine-readable storagemedium) that stores executable instructions (e.g., software, and inexample embodiments, software that comprises middleware) that, whenexecuted by the processor, facilitate performance of the operationsdescribed in FIG. 13. The user equipment can be in a vehicle (or be thevehicle), and can also operate in accordance with an operating standardrelated to connecting the moving vehicle to the mobile network (e.g., aC-V2X standard).

The example operations 1300 can comprise, at block 1310, receiving atransmission from a network device (e.g., network node 104, which in LTEcan be an eNodeB) of a mobile network via a communication channel. Thetransmission can comprise a multicast signal. The transmission cancomprise video data.

The example operations1300 can further comprise, at block 1320, decodingthe transmission using a first forward error correction code.

At block 1330, the example operations 1300 can further comprisedetermining, by the user equipment, an attribute of the transmission todetermine a condition of the communication channel. The attribute canrelate to a quality of service (e.g., bandwidth, rate of transmission,etc.). The attribute can also relate to a physical condition of thecommunication channel.

At block 1340, the example operations 1300 can further comprise, basedon the condition of the communication channel, facilitating transmittingfeedback to the network device, wherein the feedback is forwarded by thenetwork device to an application server device (e.g., C-V2X applicationserver 510) that selects a second forward error correction code based onthe feedback. In example embodiments, the feedback can be triggeredbased upon, for example, a signal to noise ratio (SNR) being too high,or a bandwidth being at a rate that is lower than agreed to in asubscriber-level agreement (e.g., SLA). Additionally, the feedback canbe triggered based on a determination that the quantity of errors in thereceived transmissions exceeded a certain rate. The facilitating thetransmitting of the feedback can comprise facilitating the transmittingvia a unicast uplink transmission channel.

The example operations 1300, at block 1350, can further comprisereceiving, by the user equipment from the network device, the secondforward error correction code.

FIG. 14 illustrates a flow diagram of example operations 1400 that canbe performed, for example, by a user equipment (e.g., C-V2X UE 505)comprising a processor and a memory (e.g., a machine-readable storagemedium) that stores executable instructions (e.g., software, and inexample embodiments, software that comprises middleware) that, whenexecuted by the processor, facilitate performance of the operationsdescribed in FIG. 14. The user equipment can be in a vehicle (or can bethe vehicle), and can also operate in accordance with an operatingstandard related to connecting the moving vehicle to the mobile network(e.g., a C-V2X standard).

The example operations 1400, at block 1410, can comprise receiving atransmission (e.g., a multicast signal comprising video data) from anetwork device of a mobile network via a communication channel.

The example operations 1400, at block 1420, can further comprisemonitoring a condition of the communication channel. The monitoring thecondition can comprise determining an attribute related to a quality ofservice. The quality of service is determined by a subscriber levelagreement. The monitoring the condition can entail, for example,determining whether a bandwidth dips below a guaranteed bandwidth basedon a subscriber level agreement of the user of the C-V2X UE, or asubscriber level agreement of the provider of a service associated withthe provision of C-V2X services.

The example operations at block 1430 can further comprise, in responseto a determination, as a result of the monitoring, that the conditionwarrants an adjustment (e.g., selection of a more suitable FEC code) toa first forward error correction code used to decode the transmission,transmitting feedback (e.g., via a unicast uplink transmission channel)to the network device, wherein the feedback is forwarded by the networkdevice (e.g., network node 104) to an application server device (e.g.,C-V2X application server 510) that selects a second forward errorcorrection code based on the feedback.

At block 1440, the operations can comprise receiving, from the networkdevice, the second forward error correction code. The user equipment canthen use the second forward error correction code to decode subsequenttransmissions it receives that were encoded using the second forwarderror correction code.

FIG. 15 illustrates a flow diagram of example operations 1500 that canbe performed, for example, by a user equipment (e.g., C-V2X UE 505)comprising a processor and a memory (e.g., a machine-readable storagemedium) that stores executable instructions (e.g., software, and inexample embodiments, software that comprises middleware) that, whenexecuted by the processor, facilitate performance of the operationsdescribed in FIG. 15. The user equipment can be in a vehicle (or be thevehicle), and can also operate in accordance with an operating standardrelated to connecting the moving vehicle to the mobile network (e.g., aC-V2X standard).

The example operations 1500 can at block 1510 comprise receiving a firsttransmission (e.g., a multicast signal comprising video data) from anetwork device of a mobile network (e.g., mobile network 106) via acommunication link.

At block 1520, the example operations 1500 can further comprisetransmitting feedback to the network device reflective of a condition ofthe communication link, wherein the feedback is forwarded by the networkdevice to an application server device, and wherein the applicationserver device selects a forward error correction code usable by userequipment to decode transmissions via the communication link. Thefeedback can indicate that a parameter associated with a quality ofservice level associated with the transmission is impacted by thecondition. The quality of service level can be specified in a subscriberlevel agreement representative of a billing arrangement associated witha customer entity associated with the user equipment.

At block 1530, the example operations 1500 can further comprisereceiving an indication from the network device to use the forward errorcorrection code. In example embodiments, the user equipment can havestored in its memory a plurality of FEC codes, including the forwarderror correction code selected by the network device.

At block 1540, the example operations 1500 can further comprise decodinga second transmission from the network device using the forward errorcorrection code.

FIG. 16 illustrates a flow diagram of example operations 1600 that canbe performed, for example, by a user equipment (e.g., C-V2X UE 505)comprising a processor and a memory (e.g., a machine-readable storagemedium) that stores executable instructions (e.g., software, and inexample embodiments, software that comprises middleware) that, whenexecuted by the processor, facilitate performance of the operationsdescribed in FIG. 16. The user equipment can be in a vehicle (or can bethe vehicle), and can also operate in accordance with an operatingstandard related to connecting the moving vehicle to the mobile network(e.g., a C-V2X standard).

The example operations 1600, at block 1610, can comprise receiving afirst transmission from a network device (e.g., network node 104) of amobile network (e.g., mobile network 106) via a communication channel.The transmission can be a multicast transmission, and can comprise videodata (e.g., live streaming video).

At block 1620, the example operations 1600 can further comprisemonitoring a condition of the communication channel. This can entaildetermining a parameter related to the condition of the communicationchannel, such as SNR, bandwidth, packet loss, latency, errors detected,etc.

At block 1630, the example operations 1600 can further comprise, inresponse to an evaluation of the condition, transmitting feedback to thenetwork device, wherein the feedback comprises an indication of aforward error correction code selected by the user equipment based onthe evaluation. The feedback can then be routed through the mobilenetwork until it reaches a C-V2X application server.

At block 1640, the example operations 1600 can comprise receiving, fromthe network device, an acknowledgement that the forward error correctioncode selected by the user equipment is to be used by the user equipmentto decode future transmissions from the network device.

Referring now to FIG. 17, illustrated is a schematic block diagram of auser equipment (e.g., UE 102, etc.) that can be a mobile device 1700(e.g., C-V2X UE 505) capable of connecting to a network in accordancewith example embodiments described herein. Although a device 1700 isillustrated herein, it will be understood that the mobile device can beother devices as well, and that the mobile device 1700 is merelyillustrated to provide context for the embodiments of the variousembodiments described herein (e.g., C-V2X automotive vehicle). Thefollowing discussion is intended to provide a brief, general descriptionof an example of a suitable environment in which the various embodimentscan be implemented. While the description includes a general context ofcomputer-executable instructions embodied on a machine-readable storagemedium, those skilled in the art will recognize that the innovation alsocan be implemented in combination with other program modules and/or as acombination of hardware and software.

Generally, applications (e.g., program modules) can include routines,programs, components, data structures, etc., that perform particulartasks or implement particular abstract data types. Moreover, thoseskilled in the art will appreciate that the methods described herein canbe practiced with other system configurations, includingsingle-processor or multiprocessor systems, minicomputers, mainframecomputers, as well as personal computers, hand-held computing devices,microprocessor-based or programmable consumer electronics, and the like,each of which can be operatively coupled to one or more associateddevices.

A computing device can typically include a variety of machine-readablemedia. Machine-readable media can be any available media that can beaccessed by the computer and includes both volatile and non-volatilemedia, removable and non-removable media. By way of example and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media can include volatileand/or non-volatile media, removable and/or non-removable mediaimplemented in any method or technology for storage of information, suchas computer-readable instructions, data structures, program modules orother data. Computer storage media can include, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, CD ROM,digital video disk (DVD) or other optical disk storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store thedesired information and which can be accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

The mobile device 1700 includes a processor 1702 for controlling andprocessing all onboard operations and functions. A memory 1704interfaces to the processor 1702 for storage of data and one or moreapplications 1706 (e.g., a video player software, user feedbackcomponent software, etc.). Other applications can include voicerecognition of predetermined voice commands that facilitate initiationof the user feedback signals. The applications 1706 can be stored in thememory 1704 and/or in a firmware 1708, and executed by the processor1702 from either or both the memory 1704 or/and the firmware 1708. Thefirmware 1708 can also store startup code for execution in initializingthe mobile device 1700. A communications component 1710 interfaces tothe processor 1702 to facilitate wired/wireless communication withexternal systems, e.g., cellular networks, VoIP networks, and so on.Here, the communications component 1710 can also include a suitablecellular transceiver 1711 (e.g., a global GSM transceiver) and/or anunlicensed transceiver 1713 (e.g., Wi-Fi, WiMax) for correspondingsignal communications. The mobile device 1700 can be a device such as acellular telephone, a PDA with mobile communications capabilities, andmessaging-centric devices. The communications component 1710 alsofacilitates communications reception from terrestrial radio networks(e.g., broadcast), digital satellite radio networks, and Internet-basedradio services networks.

The mobile device 1700 includes a display 1712 for displaying text,images, video, telephony functions (e.g., a Caller ID function), setupfunctions, and for user input. For example, the display 1712 can also bereferred to as a “screen” that can accommodate the presentation ofmultimedia content (e.g., music metadata, messages, wallpaper, graphics,etc.). The display 1712 can also display videos and can facilitate thegeneration, editing and sharing of video quotes. A serial I/O interface1714 is provided in communication with the processor 1702 to facilitatewired and/or wireless serial communications (e.g., USB, and/or IEEE1394) through a hardwire connection, and other serial input devices(e.g., a keyboard, keypad, and mouse). This supports updating andtroubleshooting the mobile device 1700, for example. Audio capabilitiesare provided with an audio I/O component 1716, which can include aspeaker for the output of audio signals related to, for example,indication that the user pressed the proper key or key combination toinitiate the user feedback signal. The audio I/O component 1716 alsofacilitates the input of audio signals through a microphone to recorddata and/or telephony voice data, and for inputting voice signals fortelephone conversations.

The mobile device 1700 can include a slot interface 1718 foraccommodating a SIC (Subscriber Identity Component) in the form factorof a card Subscriber Identity Module (SIM) or universal SIM 1720, andinterfacing the SIM card 1720 with the processor 1702. However, it is tobe appreciated that the SIM card 1720 can be manufactured into themobile device 1700, and updated by downloading data and software.

The mobile device 1700 can process IP data traffic through thecommunications component 1710 to accommodate IP traffic from an IPnetwork such as, for example, the Internet, a corporate intranet, a homenetwork, a person area network, etc., through an ISP or broadband cableprovider. Thus, VoIP traffic can be utilized by the mobile device 1700and IP-based multimedia content can be received in either an encoded ordecoded format.

A video processing component 1722 (e.g., a camera) can be provided fordecoding encoded multimedia content. The video processing component 1722can aid in facilitating the generation, editing and sharing of videoquotes. The mobile device 1700 also includes a power source 1724 in theform of batteries and/or an AC power subsystem, which power source 1724can interface to an external power system or charging equipment (notshown) by a power I/O component 1726.

The mobile device 1700 can also include a video component 1730 forprocessing video content received and, for recording and transmittingvideo content. For example, the video component 1730 can facilitate thegeneration, editing and sharing of video quotes. A location trackingcomponent 1732 facilitates geographically locating the mobile device1700. As described hereinabove, this can occur when the user initiatesthe feedback signal automatically or manually. A user input component1734 facilitates the user initiating the quality feedback signal. Theuser input component 1734 can also facilitate the generation, editingand sharing of video quotes. The user input component 1734 can includesuch conventional input device technologies such as a keypad, keyboard,mouse, stylus pen, and/or touch screen, for example.

Referring again to the applications 1706, a hysteresis component 1736facilitates the analysis and processing of hysteresis data, which isutilized to determine when to associate with the access point. Asoftware trigger component 1738 can be provided that facilitatestriggering of the hysteresis component 1738 when the Wi-Fi transceiver1713 detects the beacon of the access point. A SIP client 1740 enablesthe mobile device 1700 to support SIP protocols and register thesubscriber with the SIP registrar server. The applications 1706 can alsoinclude a client 1742 that provides at least the capability ofdiscovery, play and store of multimedia content, for example, music.

The mobile device 1700, as indicated above related to the communicationscomponent 1710, includes an indoor network radio transceiver 1713 (e.g.,Wi-Fi transceiver 1713). This function supports the indoor radio link,such as IEEE 802.11, for the mobile device 1700. The mobile device 1700can accommodate at least satellite radio services through a mobiledevice that can combine wireless voice and digital radio chipsets into asingle handheld device.

Referring now to FIG. 18, there is illustrated a block diagram of acomputer 1800 that can execute the functions and operations performed inthe described example embodiments. For example, network node 104, C-V2Xapplication server 510, can contain components as described in FIG. 18.The computer 1800 can provide networking and communication capabilitiesbetween a wired or wireless communication network and a server and/orcommunication device. In order to provide additional context for variousaspects thereof, FIG. 18 and the following discussion are intended toprovide a brief, general description of a suitable computing environmentin which the various aspects of the embodiments can be implemented tofacilitate the functions and operations described herein. While thedescription above is in the general context of computer-executableinstructions that can run on one or more computers, those skilled in theart will recognize that the embodiments also can be implemented incombination with other program modules and/or as a combination ofhardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the various methods can be practiced with other computer systemconfigurations, comprising single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the embodiments can also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and comprises both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

Communications media can embody computer-readable instructions, datastructures, program modules or other structured or unstructured data ina data signal such as a modulated data signal, e.g., a carrier wave orother transport mechanism, and comprises any information delivery ortransport media. The term “modulated data signal” or signals refers to asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in one or more signals. By way ofexample, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

With reference to FIG. 18, implementing various aspects describedherein, devices can include a computer 1800, the computer 1800comprising a processing unit 1804, a system memory 1806 and a system bus1808. The system bus 1808 couples system components comprising thesystem memory 1806 to the processing unit 1804. The processing unit 1804can be any of various commercially available processors. Dualmicroprocessors and other multi-processor architectures can also beemployed as the processing unit 1804.

The system bus 1808 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1806comprises read-only memory (ROM) 1827 and random access memory (RAM)1812. A basic input/output system (BIOS) is stored in a non-volatilememory 1827 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1800, such as during start-up. The RAM 1812 can also include ahigh-speed RAM such as static RAM for caching data.

The computer 1800 further comprises an internal hard disk drive (HDD)1814 (e.g., EIDE, SATA), which internal hard disk drive 1814 can also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 1816, (e.g., to read from or write to aremovable diskette 1818) and an optical disk drive 1820, (e.g., readinga CD-ROM disk 1822 or, to read from or write to other high capacityoptical media such as the DVD). The hard disk drive 1814, magnetic diskdrive 1816 and optical disk drive 1820 can be connected to the systembus 1808 by a hard disk drive interface 1824, a magnetic disk driveinterface 1826 and an optical drive interface 1828, respectively. Theinterface 1824 for external drive implementations comprises at least oneor both of Universal Serial Bus (USB) and IEEE 1294 interfacetechnologies. Other external drive connection technologies are withincontemplation of the subject embodiments.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1800 the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer 1800, such aszip drives, magnetic cassettes, flash memory cards, cartridges, and thelike, can also be used in the example operating environment, andfurther, that any such media can contain computer-executableinstructions for performing the methods of the disclosed embodiments.

A number of program modules can be stored in the drives and RAM 1812,comprising an operating system 1830, one or more application programs1832, other program modules 1834 and program data 1836. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1812. It is to be appreciated that the embodiments canbe implemented with various commercially available operating systems orcombinations of operating systems.

A user can enter commands and information into the computer 1800 throughone or more wired/wireless input devices, e.g., a keyboard 1838 and apointing device, such as a mouse 1840. Other input devices (not shown)can include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, remote terminal, or the like. These andother input devices are often connected to the processing unit 1804through an input device interface 1842 that is coupled to the system bus1808, but can be connected by other interfaces, such as a parallel port,an IEEE 2394 serial port, a game port, a USB port, an IR interface, etc.

A monitor 1844 or other type of display device can be connected to thesystem bus 1808 through an interface, such as a video adapter 1846. Inaddition to the monitor 1844, the computer 1800 can comprise otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1800 can operate in a networked environment using logicalconnections by wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1848. The remotecomputer(s) 1848 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentdevice, a peer device or other common network node, and typicallycomprises many, if not all of, the elements described relative to thecomputer, although, for purposes of brevity, only a memory/storagedevice 1850 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 1852 and/orlarger networks, e.g., a wide area network (WAN) 1854. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich can connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 1800 isconnected to the local network 1852 through a wired and/or wirelesscommunication network interface or adapter 1856. The adapter 1856 canfacilitate wired or wireless communication to the LAN 1852, which canalso include a wireless access point disposed thereon for communicatingwith the wireless adapter 1856.

When used in a WAN networking environment, the computer 1800 can includea modem 1858, or is connected to a communications server on the WAN1854, or has other means for establishing communications over the WAN1854, such as by way of the Internet. The modem 1858, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1808 through the input device interface 1842. In a networkedenvironment, program modules depicted relative to the computer, orportions thereof, can be stored in the remote memory/storage device1850. It will be appreciated that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers can be used.

The computer can communicate with any wireless devices or entitiesoperatively disposed in wireless communication, e.g., a printer,scanner, desktop and/or portable computer, portable data assistant,communications satellite, any piece of equipment or location associatedwith a wirelessly detectable tag (e.g., a kiosk, news stand, restroom),and telephone. This comprises at least Wi-Fi and Bluetooth™ wirelesstechnologies. Thus, the communication can be a predefined structure aswith a conventional network or simply an ad hoc communication between atleast two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE802.11 (a, b,g, n, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE802.3 or Ethernet). Wi-Finetworks operate in the unlicensed 2.4 and 5 GHz radio bands, at an 11Mbps (802.11b) or 54 Mbps (802.11a) data rate, for example, or withproducts that contain both bands (dual band), so the networks canprovide real-world performance similar to the basic “10BaseT” wiredEthernet networks used in many offices.

As used in this application, the terms “system,” “component,”“interface,” and the like are generally intended to refer to acomputer-related entity or an entity related to an operational machinewith one or more specific functionalities. The entities disclosed hereincan be either hardware, a combination of hardware and software,software, or software in execution. For example, a component can be, butis not limited to being, a process running on a processor, a processor,an object, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running on aserver and the server can be a component. One or more components canreside within a process and/or thread of execution and a component canbe localized on one computer and/or distributed between two or morecomputers. These components also can execute from various computerreadable storage media comprising various data structures storedthereon. The components can communicate via local and/or remoteprocesses such as in accordance with a signal comprising one or moredata packets (e.g., data from one component interacting with anothercomponent in a local system, distributed system, and/or across a networksuch as the Internet with other systems via the signal). As anotherexample, a component can be an apparatus with specific functionalityprovided by mechanical parts operated by electric or electroniccircuitry that is operated by software or firmware application(s)executed by a processor, wherein the processor can be internal orexternal to the apparatus and executes at least a part of the softwareor firmware application. As yet another example, a component can be anapparatus that provides specific functionality through electroniccomponents without mechanical parts, the electronic components cancomprise a processor therein to execute software or firmware thatconfers at least in part the functionality of the electronic components.An interface can comprise input/output (I/O) components as well asassociated processor, application, and/or API components.

Furthermore, the disclosed subject matter can be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques to produce software, firmware, hardware,or any combination thereof to control a computer to implement thedisclosed subject matter. The term “article of manufacture” as usedherein is intended to encompass a computer program accessible from anycomputer-readable device, computer-readable carrier, orcomputer-readable media. For example, computer-readable media caninclude, but are not limited to, a magnetic storage device, e.g., harddisk; floppy disk; magnetic strip(s); an optical disk (e.g., compactdisk (CD), a digital video disc (DVD), a Blu-ray Disc™ (BD)); a smartcard; a flash memory device (e.g., card, stick, key drive); and/or avirtual device that emulates a storage device and/or any of the abovecomputer-readable media.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising single-core processors; single-processors with softwaremultithread execution capability; multi-core processors; multi-coreprocessors with software multithread execution capability; multi-coreprocessors with hardware multithread technology; parallel platforms; andparallel platforms with distributed shared memory. Additionally, aprocessor can refer to an integrated circuit, an application specificintegrated circuit (ASIC), a digital signal processor (DSP), a fieldprogrammable gate array (FPGA), a programmable logic controller (PLC), acomplex programmable logic device (CPLD), a discrete gate or transistorlogic, discrete hardware components, or any combination thereof designedto perform the functions described herein. Processors can exploitnano-scale architectures such as, but not limited to, molecular andquantum-dot based transistors, switches and gates, in order to optimizespace usage or enhance performance of UE. A processor also can beimplemented as a combination of computing processing units.

In the subject specification, terms such as “store,” “data store,” “datastorage,” “database,” “repository,” “queue”, and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can comprise both volatile andnonvolatile memory. In addition, memory components or memory elementscan be removable or stationary. Moreover, memory can be internal orexternal to a device or component, or removable or stationary. Memorycan comprise various types of media that are readable by a computer,such as hard-disc drives, zip drives, magnetic cassettes, flash memorycards or other types of memory cards, cartridges, or the like.

By way of illustration, and not limitation, nonvolatile memory cancomprise read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can comprise random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

In particular and in regard to the various functions performed by theabove described components, devices, circuits, systems and the like, theterms (comprising a reference to a “means”) used to describe suchcomponents are intended to correspond, unless otherwise indicated, toany component which performs the specified function of the describedcomponent (e.g., a functional equivalent), even though not structurallyequivalent to the disclosed structure, which performs the function inthe herein illustrated example aspects of the embodiments. In thisregard, it will also be recognized that the embodiments comprises asystem as well as a computer-readable medium comprisingcomputer-executable instructions for performing the acts and/or eventsof the various methods.

Computing devices typically comprise a variety of media, which cancomprise computer-readable storage media and/or communications media,which two terms are used herein differently from one another as follows.Computer-readable storage media can be any available storage media thatcan be accessed by the computer and comprises both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media cancomprise, but are not limited to, RAM, ROM, EEPROM, flash memory orother memory technology, CD-ROM, digital versatile disk (DVD) or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or other tangible and/ornon-transitory media which can be used to store desired information.Computer-readable storage media can be accessed by one or more local orremote computing devices, e.g., via access requests, queries or otherdata retrieval protocols, for a variety of operations with respect tothe information stored by the medium.

On the other hand, communications media typically embodycomputer-readable instructions, data structures, program modules orother structured or unstructured data in a data signal such as amodulated data signal, e.g., a carrier wave or other transportmechanism, and comprises any information delivery or transport media.The term “modulated data signal” or signals refers to a signal that hasone or more of its characteristics set or changed in such a manner as toencode information in one or more signals. By way of example, and notlimitation, communications media comprise wired media, such as a wirednetwork or direct-wired connection, and wireless media such as acoustic,RF, infrared and other wireless media

Further, terms like “user equipment,” “user device,” “mobile device,”“mobile,” station,” “access terminal,” “terminal,” “handset,” andsimilar terminology, generally refer to a wireless device utilized by asubscriber or user of a wireless communication network or service toreceive or convey data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream. The foregoing termsare utilized interchangeably in the subject specification and relateddrawings. Likewise, the terms “access point,” “node B,” “base station,”“evolved Node B,” “cell,” “cell site,” and the like, can be utilizedinterchangeably in the subject application, and refer to a wirelessnetwork component or appliance that serves and receives data, control,voice, video, sound, gaming, or substantially any data-stream orsignaling-stream from a set of subscriber stations. Data and signalingstreams can be packetized or frame-based flows. It is noted that in thesubject specification and drawings, context or explicit distinctionprovides differentiation with respect to access points or base stationsthat serve and receive data from a mobile device in an outdoorenvironment, and access points or base stations that operate in aconfined, primarily indoor environment overlaid in an outdoor coveragearea. Data and signaling streams can be packetized or frame-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,” andthe like are employed interchangeably throughout the subjectspecification, unless context warrants particular distinction(s) amongthe terms. It should be appreciated that such terms can refer to humanentities, associated devices, or automated components supported throughartificial intelligence (e.g., a capacity to make inference based oncomplex mathematical formalisms) which can provide simulated vision,sound recognition and so forth. In addition, the terms “wirelessnetwork” and “network” are used interchangeable in the subjectapplication, when context wherein the term is utilized warrantsdistinction for clarity purposes such distinction is made explicit.

Moreover, the word “exemplary,” where used, is used herein to meanserving as an example, instance, or illustration. Any aspect or designdescribed herein as “exemplary” is not necessarily to be construed aspreferred or advantageous over other aspects or designs. Rather, use ofthe word exemplary is intended to present concepts in a concretefashion. As used in this application, the term “or” is intended to meanan inclusive “or” rather than an exclusive “or”. That is, unlessspecified otherwise, or clear from context, “X employs A or B” isintended to mean any of the natural inclusive permutations. That is, ifX employs A; X employs B; or X employs both A and B, then “X employs Aor B” is satisfied under any of the foregoing instances. In addition,the articles “a” and “an” as used in this application and the appendedclaims should generally be construed to mean “one or more” unlessspecified otherwise or clear from context to be directed to a singularform.

In addition, while a particular feature may have been disclosed withrespect to only one of several implementations, such feature can becombined with one or more other features of the other implementations asmay be desired and advantageous for any given or particular application.Furthermore, to the extent that the terms “have”, “having”, “includes”and “including” and variants thereof are used in either the detaileddescription or the claims, these terms are intended to be inclusive in amanner similar to the term “comprising.”

The above descriptions of various embodiments of the subject disclosureand corresponding figures and what is described in the Abstract, aredescribed herein for illustrative purposes, and are not intended to beexhaustive or to limit the disclosed embodiments to the precise formsdisclosed. It is to be understood that one of ordinary skill in the artcan recognize that other embodiments comprising modifications,permutations, combinations, and additions can be implemented forperforming the same, similar, alternative, or substitute functions ofthe disclosed subject matter, and are therefore considered within thescope of this disclosure. Therefore, the disclosed subject matter shouldnot be limited to any single embodiment described herein, but rathershould be construed in breadth and scope in accordance with the claimsbelow.

What is claimed is:
 1. A method, comprising: by network equipmentcomprising a processor, receiving feedback from a user equipment, thefeedback comprising a condition of a communication channel between theuser equipment and the network equipment determined based on attributedata representative of an attribute of a transmission received by theuser equipment and decoded using a first forward error correction code;selecting, by the network equipment, a second forward error correctioncode based on the feedback; and facilitating, by the network equipment,transmitting the second forward error correction code to the userequipment.
 2. The method of claim 1, wherein the attribute relates to abandwidth of the communication channel.
 3. The method of claim 1,wherein the attribute relates to a signal-to-noise ratio of thecommunication channel.
 4. The method of claim 1, wherein the attributerelates to an error rate of the communication channel.
 5. The method ofclaim 1, wherein the attribute relates to a latency of the communicationchannel.
 6. The method of claim 1, wherein the user equipment is part ofa vehicle.
 7. The method of claim 1, wherein facilitating the receivingof the feedback comprises facilitating the receiving of the feedback viaa unicast uplink transmission channel
 8. Network equipment, comprising:a processor; and a memory that stores executable instructions that, whenexecuted by the processor, facilitate performance of operations,comprising: obtaining a report from a user equipment, the reportcomprising a condition of a communication channel between the userequipment and the network equipment determined based on an attribute ofa transmission received by the user equipment and decoded using a firstforward error correction code; choosing a second forward errorcorrection code based on the report; and communicating the secondforward error correction code to the user equipment.
 9. The networkequipment of claim 8, wherein the attribute corresponds to a bandwidthof the communication channel.
 10. The network equipment of claim 8,wherein the attribute corresponds to a signal-to-noise ratio of thecommunication channel.
 11. The network equipment of claim 8, wherein theattribute corresponds to an error rate of the communication channel. 12.The network equipment of claim 8, wherein the attribute corresponds to alatency of the communication channel.
 13. The network equipment of claim8, wherein the user equipment is part of a vehicle.
 14. The networkequipment of claim 8, wherein obtaining the report comprises obtainingthe report via a unicast uplink transmission channel
 15. Anon-transitory machine-readable medium, comprising executableinstructions that, when executed by a processor of network equipment,facilitate performance of operations, comprising: receiving an alertfrom a vehicle, the alert comprising a condition of a communication linkbetween the vehicle and the network equipment determined based onattribute data representative of an attribute of a transmission receivedby the vehicle and decoded using a first forward error correction code;selecting a second forward error correction code based on the alert; andtransmitting the second forward error correction code to the vehicle.16. The non-transitory machine-readable medium of claim 15, wherein theattribute data comprises bandwidth data representative of a bandwidth ofthe communication link.
 17. The non-transitory machine-readable mediumof claim 15, wherein the attribute ratio data comprises bandwidth datarepresentative of a signal-to-noise ratio of the communication link. 18.The non-transitory machine-readable medium of claim 15, wherein theattribute data comprises error rate data representative of an error rateof the communication link.
 19. The non-transitory machine-readablemedium of claim 15, wherein the attribute data comprises latency datarepresentative of a latency of the communication link.
 20. Thenon-transitory machine-readable medium of claim 15, wherein receivingthe alert comprises receiving the alert via a unicast uplinktransmission link.